Could you describe the use case and how this is a problem ?

The meshes are meant to be automatically hidden/shown when they are within a certain range of the angle where the mesh was created. The meshes are only valid for a certain projection. see

This is perhaps not behaving as you wish ?

Could you describe the use case and how this is a problem ?

This is an attempt to fix following bug:

• create a mesh
• hide the mesh via the hide button
• do a data collection, say standard oscillation data collection

After the data collection is finished, the mesh will be un-hidden.

The behavior we want is that meshes explicitly hidden by the user are never automatically un-hidden.

Ah, we should perhaps then add an option to disable the auto hide/show option ?

Ah, we should perhaps then add an option to disable the auto hide/show option ?

I think the current behavior is fine. The users so far have not complained about meshes getting hidden during data collections, scans, etc.

It's only the part where all meshes become visible after the scan is finished that annoys users.

Also, here is the MXCuBE-web part of the bug fix: mxcube/mxcubeweb#1460

It's only the part where all meshes become visible after the scan is finished that annoys users.

I see, is that because all the meshes where created at the same angle or for some other reason. Why is all meshes shown when the collection finishes ?

It's only the part where all meshes become visible after the scan is finished that annoys users.

I see, is that because all the meshes where created at the same angle or for some other reason. Why is all meshes shown when the collection finishes ?

Yes, it is a common usage scenario at MicroMAX right now. Users use large chips to collect data. They draw a number of mesh grids at the same angle, as the chip don't rotate.

The reason all mesh grids are made visible, is because the code that auto-hides grids does something like this:

grid.status = "hidden"

Thus the information if a grids was hidden by the user is lost. When code that un-hides grids runs, it shows all grids with correct angle.

I see, I'm hesitant on adding a user_state. As far as I remember, and I had a quick look, the only place where we update the shape state to "HIDDEN" is in:

The drawing of the shapes on the canvas is not performed when the goniometer motors are moving but updated when the state changes to ready. Or did I perhaps leave something out ?

I guess in that case what is causing you this issue is that the state gets changed on rotation, maybe simply adding a option that disables the code above would be enough ?. You could perhaps try to comment out that section and see if it helps ?

I see, I'm hesitant on adding a user_state. As far as I remember, and I had a quick look, the only place where we update the shape state to "HIDDEN" is in:

You are right, the Shape.state is set only in the linked code.

I've talked with @elmjag and the desired functionality looks like this:

• if user sets grid to HIDDEN manually - keep it hidden always
• If user sets grid to 'SAVED' - it may become hidden anyways due to rotating (just like it is now)

This would require to store the user's preference somewhere, e.g., in the user_state attribute.

The problem I see with this feature is that it clashes with the idea of auto hiding. The user would after some time not know which meshes are not being shown because they are auto hidden or explicitly hidden. I guess in that case it should be more evident in the grid list why a grid is hidden. I somehow thing that this might lead to some confusion, thats why I'm a bit hesitant.

It would perhaps be possible to always display a dashed outline of hidden grids or highlight them in the grid table, not sure what would be the best.

It would perhaps be possible to always display a dashed outline of hidden grids or highlight them in the grid table, not sure what would be the best.

I think you're right there; I've made some changes on the UI part so that the user-hidden grids appear with a darker background.

I've also pushed some changes to this repository. I've updated the functions that redraw the shapes, to be able to persist the state and user_state attributes.